fix(studio): preserve reused MCP credentials across debug and deploy - #1088
Merged
yaozheng-fang merged 4 commits intoSep 9, 2026
Merged
Conversation
yaozheng-fang
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
authTokenEnvand legacyMCP_SERVERS_JSONstate/mcpRoot cause
The deploy path transported explicit reuse decisions, but the ordinary-Agent debug path did not always restore the corresponding server-held credential. Debug could then attempt anonymous discovery and collapse unrelated failures into one HTTP 422. Separately, the UI treated every non-
/mcppath as suspicious even though MCP endpoints can use arbitrary business paths, and invalid legacy URLs could escape the existing HTTP mapping as HTTP 500.Verification
/athena-mcppath, Bearer authentication, initialize/session negotiation, andtools/listNo Release Server, Studio Release, production TOS, customer FaaS, or existing Agent mutation is included in this PR.